projects / gtk4.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b74aec3) | patch
Don't invalidate parent if it didn't change
authorBenjamin Otte <otte.benjamin@googlemail.com>
Fri, 6 May 2022 11:50:55 +0000 (11:50 +0000)
committerBenjamin Otte <otte.benjamin@googlemail.com>
Fri, 6 May 2022 11:50:55 +0000 (11:50 +0000)
commitc29bf115f2317d1df57c55509074937529467948
tree36fbe537563f9af334c3e91fbc39ed25d26656e9tree | snapshot
parentb74aec360602c52a5cc41175d322df5f971f9d4ccommit | diff
Don't invalidate parent if it didn't change

This looks like a leftover excess invalidation from when the surrounding
code was refactored to not just be called on parent changes but also
when repositioning inside the same parent in commit
507016cafc407b2c47aea3fd1483df75e9757f29

Ivan Molodetskikh found this problem in
https://gitlab.gnome.org/GNOME/gtk/-/issues/3334#note_1445873 which
contains a longer analysis of this problem and the performance
reductions it causes.

Related: #3334
gtk/gtkcssnode.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.